home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
ffix121.arc
/
FILEFIX.NWS
< prev
next >
Wrap
Text File
|
1991-05-15
|
13KB
|
302 lines
'+' lines are new/enhanced features.
'-' lines are bugfixes or stupid things fixed.
'!' lines are changes, i.e. things that work different now.
News in version 1.21
--------------------
- Fixed bug where FILEFIX.FFX would never be utilized. In other words,
v1.20 was just as slow as the previous versions!
- The path in your okfile would errornously be set to your netfile
directory - now it is set to the destination directory for the file.
+ New keyword, KeepLatest. This is used to retain only the newest X
versions of a file online. If you want to keep the last 3 z2-diff's:
KeepLatest 3 C:\FILES\NODELIST\Z2-DIFF.A??
.. will do the job. This feature works exactly as it does in X_List.
+ New commandline command, CLEANUP, which performs cleanup processing.
This command should be run as part of your daily cleanup and performs
various FileFix cleanup processing.. At the moment, the only cleanup
performed is the 'KeepLatest' stuff above.
News in version 1.20
--------------------
- The timestamp file (FILEFIX.TIM) would be updated after every
run, instead of only when the forward function was performed. So
the 'Date' condition would not work in many cases.
- FileFix will now skip any debris at the end of lines (such as
comments) in messages from nodes/points.
- FileFix will now properly strip a Ctrl-Z at the end of
Files.Bbs when appending a new file.
- FileFix will now (it will now a lot of things :-) write
^AINTL-kludges without a ':' (although the ':' should be there
according to FTS-0001..).
+ New option, 'ForceIntl', which causes FileFix to _always_ add
an ^AINTL line to messages that it writes.
+ The name that FileFix will react to in netmail can be changed
with the new keyword 'FileFixName'.
+ New command, SUBMIT, which is used to perform forward processing
for a single specified file. This command is meant to be used
for sending out files that you maintain. There is also a new
attribute "Manual" for the condition field - when this is set,
FileFix will never automatically forward this file. Usage,
FILEFIX SUBMIT <MAGIC> [MASK]
If MASK is not specified, the mask from filefix.cfg is used. Example,
FILEFIX SUBMIT FIDONEWS
.. or ..
FILEFIX SUBMIT DANENEWS C:\STUFF\DANENEWS.A23
+ If the first character of the destination directory for a file
is '-', then FileFix will not actually move the file, but otherwise
act as if the file had been moved (update files.bbs in the dest-dir,
etc.). This is meant to be used in conjunction with OtherSw<tm>,
that later moves the file.
+ The new keyword "Swap" for filefix.cfg will make FileFix swap
itself to disk or EMS when executing batch procedures. It should
only be nessesary to use swapping if you run utilities that
demands obscene amounts of memory - FileFix uses only
around 100k of memory..
+ Built-in "fixer" for the bug in the TosScan 1.0 AreaMgr. Enabled
with the keyword "AMgrFix" in filefix.cfg. AreaMgr messages are
then fixed whenever FileFix SCAN or BOTH is run. FileFix will
exit with errorlevel 99 if any messages were fixed.
+ The ^APID kludge is now added to messages instead of a tearline.
+ FileFix can now help you maintain magic names in your OKFILE.
If you name your okfile (FrontDoor: Alias file) in FileFix.Cfg with
the 'Okfile' keyword, FileFix will check it whenever it forwards
a file. Say you have 'Z2-DIFF C:\FILES\Z2-DIFF.A69' - when FileFix
forwards Z2-DIFF.A77, it will update the above line with the
new filename.
+ Whenever the forward function finds a file to forward, it
will write a record to the history file with nodeno. 0:0/0.0.
This record will later be used by the dupechecker.
+ Lines in FileFix.Are can now be upto 1024 characters long
(the previous limit was 132 characters).
+ Nodes/points can now use '-r' (AreaFix: rescan) in the subject line
whenever they connect to a file. When FileFix sees this, it will
immediately robot them the latest revision of the magic file that
they connect to. For instance: A node connects itself to FIDONEWS.
You have FNEWS741.ARC and FNEWS742.ARC online. FileFix will send the
node FNEWS742.ARC at once if '-r' was used.
+ If '-?' was used in the subject, then FileFix will send the
usage-file to the node asking for help. The usage-file is by
default FILEFIX.USE, but you can override this with the
'Usagefile' keyword in FileFix.Cfg. If there is an error in the
message to FileFix, it will send back a message to the user telling
him (or her :-) about the '-?' option.
+ There is a sample FILEFIX.USE written by Lars J¢rgensen (2:231/16.32)
in the distribution archive. If you want to make it available for
filerequest or download seperately, then please name the archive
FF_USE.xxx - thanks.
+ In the batch function, some new parameters will now be passed to your
batchfile. Assuming that we're processing the file
C:\NODELIST\Z2-DIFF.A27, which is dated 07-Feb-1990:
Parameter Contains Example Note
--------- ---------------------- ----------------------- -----------
%1 Full filename C:\NODELIST\Z2-DIFF.A27
%2 Drive C No ':'
%3 Directory of filename \NODELIST No trailing '\'
%4 Base filename Z2-DIFF No '.'
%5 Extension A27 No '.'
%6 Day of the year 038 Always 3 digits
%7 Last two digits of %6 38 Always 2 digits
You can use them to construct new filenames. %1 is just a shortcut,
it is actually the same as '%2:%3\%4.%5'. All parameters are always
in uppercase. %7 is what is used for nodelist diffs, FidoNews, etc.
+ New commandline parameter, '-r'. It tells FileFix to ignore the
"received" flag in messages to FileFix. This is a workaround for
editors that always marks messages received, even though they're
not to the SysOp. '-r' should _never_ be used together with
the configurationfile keyword 'KeepProcessed'!
+ "FileFix Scan" (and "FileFix Both") are much faster, since the
scan function will only open/read messages that have changed
since the last run of the scan function. E.g., only .MSG files
with date/time stamp higher than the date/time stamp of
FILEFIX.FFX will be processed. FILEFIX.FFX will be created/updated
in your netmail directory each time a scan is done. It is a
zero-byte file, so it does not consume any diskspace; just a directory
entry.
NOTICE: If you use the 'KeepDays' option, then FileFix will _not_
use FILEFIX.FFX. Because? Because, if KeepDays is to work, FileFix
will have to check the old messages too, which will not be done
if FILEFIX.FFX is utilized.
+ Batch functions may now repack the processed file. But you have
to tell FileFix about it! This is done by supplying the new
file extension as second parameter to the Batch statement, like this:
Batch FIDONEWS ZIP
Which would tell FileFix to check if the file had changed extension
to .ZIP while performing the batch sequence (it is ok if it doesn't).
News in version 1.17
--------------------
- Patch to work around the problem with ':' in INTL lines.
News in version 1.16
--------------------
- This was a patch to fix a problem in the file move function, where
files 32k in size or above were truncated to 0 bytes, while moving
them to another disk.
News in version 1.15
--------------------
o If you had the history feature enabled, FileFix would forget to
close a file each time it forwarded one. So if many forwards
were done in a single run, FileFix would eventually run out of
file handles and claim it couldn't open some odd file (and then
proceed to crash..).
o New keyword, LogStyle, which allows you to determine what kind
of logfile FileFix should maintain. Currently the FrontDoor, QuickBBS,
and Opus/Binkley formats are available.
o If the string 'NO-MOVE' is used in place of the destination
directory, FileFix won't move the file anywhere when it sees it.
o If you do not use 'AttachMsg' in FileFix.Cfg, FileFix will now
create a null message (e.g. no message body at all).
o Added individual message flags to nodes in FileFix.Cfg. You can
now make messages crash, hold and keep (not kill/sent).
News in version 1.10
--------------------
o New limit: Maximum number of files/files per node is 100 (was 20).
o In the previous version FileFix would compare the first 3 characters
of a file in order to find its proper place in Files.Bbs. This version
compares upto the first '.', '*' or '?' in the filename instead, so
the file should be placed properly in Files.?bs in almost all cases.
o FileFix would get mightily confused if Files.Bbs or Files.Gbs happened to
be a directory - repaired.
o If '%cookie' was used in FileFix.Msg and no cookiefile was defined,
FileFix would emit garbage to the message - repaired.
o New keywords 'Batch' and 'EndBatch'. Executes batch commands whenever
a file is about to be forwarded (for unpacking the nodediff, updating
bulletin's, etc.). Check FileFix.Cfg for sample usage.
o Option to retain a history of which files are robotted where and when.
Enabled with the 'history' statement in FileFix.Cfg, viewed/printed
with the 'list' command and purged with the 'pack' command.
o If '-x' was used, FileFix would insert '0' in place of %zone, %point,
%address, %dzone, %dpoint and %daddress in messages. Repaired.
o Support for mixed use of real and fake point addresses. If you use
'PointNet' in FileFix.Cfg, you can give real point addresses in
the 'Node' statements in FileFix.Cfg, even though your points
write to FileFix using fake addresses.
o "X_List compatible" forwarding, that is, a file is only forwarded if
its timestamp is newer or equal to the last time FileFix was run. This
is enabled by using 'Date' in place of the weekdays in the 'File'
statement in FileFix.Cfg.
o FileFix won't attempt to move a file to itself - that is, if you
set a files destination directory to its source directory (usually
your netfile directory), the file will stay there and FileFix
won't panic.
o Minor cosmethic changes and minor bugfixes..
News in version 1.05
--------------------
o -c<cfgfile> option lets you use a configuration file different from
"FileFix.Cfg".
o -a<areasfile> option lets you use an areas file different from
"FileFix.Are".
o Option '-x' avoids use of new fields in the message header. These
fields are in the newer versions of FTS-0001, but some software
doesn't like them (ME2 for instance...). If the message date or
anything else seems odd in FileFix generated messages, try to use
this switch.
o In FileFix.Cfg, the format of the 'File' statement has changed, to
allow for forwarding of files only on certain weekdays. You must
edit your existing FileFix.Cfg to the new format, which is as follows:
File <magic> <group> <mask> <destdir> <weekday(s)> <description>
^^^^^^^^^^^^ new field..
Weekdays is either "All", or a string of two-character weekday
abbreviations, such as "MoThSa" (this file would only be forwarded
on mondays, thursdays and saturdays).
o Better error checking.
o Command "REPORT [filename]" will create a simple report over
which nodes are receiving what files. If no filename is specified,
CON (the screen) is used as output file.
o Commandline option '-?' displays all commands and options available.
o In the files descriptions ('File' stmt. in Filefix.cfg), you can now
insert variable data depending on the name of the file being shipped.
For instance, if FidoNews had the description,
"FidoNet newsletter vol. %6, issue %7%8"
.. a shipment of "FNEWS714.ZIP" would generate a description as ..
"FidoNet newsletter vol. 7, issue 14"
In other words, if you use '%n' in a description (n=some number),
that character will be replaced with the corresponding character
from the filename.
o If you use the 'AutoAdopt' keyword in Filefix.Cfg, FileFix will
automatically insert new files in Files.Bbs/Files.Gbs (if they
exist). The files description will be taken from its description
in Filefix.Cfg. FileFix will make an educated guess as to where
in Files.Bbs to place the new file - it will usually place the new
file after the last "similar" file in the area (now you figure out
what THAT means!).
o A different name can be specified as the sender of messages generated
by FileFix (your name for instance).
### EOF ###